Skip to main content
This page covers the create and share flow. For the concept, see Share with Collections.

​
How to create a Collection

1

Go to Collections

Click Collections under Discover in the sidebar. The My collections tab lists every collection you created.
2

Click New Collection

Click New Collection in the top right. The Create a new Collection dialog opens.
3

Name and describe

Pick a clear name. The description is for recipients to understand what the Collection contains. Click Create Collection. The dialog closes and the new Collection appears in your list.
4

Add apps

Open the new Collection and click Add apps in the top right. Search for apps you have access to and pick the ones to include. You can change the contents anytime.
The New Collection button appears only if you can create Collections in your organization. Org Owners, Builders, and Editors can. If you don’t see it, ask an org Owner about your role.

​
How to share a Collection

1

Open the Collection

Open the Collection from Discover → Collections.
2

Click Share

The Share button is in the top right of the Collection’s page. You can also choose Share collection from the Collection card’s ⋮ menu on the Collections list.
3

Type the recipient

Add a person who shares one of your organizations, a group in one of your organizations, or an organization you belong to. You can’t share with organizations you aren’t a member of. Each recipient is added as soon as you pick them.
4

Set permissions

New recipients start as User, which is the right level for most cases. To change it, pick another role from the recipient’s role dropdown.
5

Click Done

Click Done to close the dialog. The Collection appears for each recipient. They can use the apps directly, and Space Owners and Managers can add it to their spaces.

​
Updating a Collection

A Collection’s contents aren’t fixed. From the Collection’s page, click Add apps in the top right to add more, or use an app card’s ⋮ menu to Remove from collection. Removing an app takes it out of the Collection without deleting it. For the full walkthrough, see Managing apps in a Collection. Recipients see the updated set on their next visit. They do not need to re-add the Collection. Apps you remove disappear from recipient views; apps you add appear automatically. When the owner of an app inside the Collection publishes a new version, recipients see the new version too. Updates flow through the Collection.

​
Permission levels for Collections

User (most common) Recipients can use the apps in the Collection. They cannot edit the Collection itself or the apps inside. Editor (rare) Recipients can add or remove apps and share the Collection. Useful for co-curation. Editors can add only apps they have access to use. Owner Everything an Editor can do, plus delete the Collection. Only Owners can make someone else an Owner or change an Owner’s role. For most partner deployments, User is the right level. Editor is for collaborative curation between trusted partners.

​
Key points

  • Create from Discover → Collections, name it, and add apps
  • Share via a Share dialog like the one for apps (individuals, groups, orgs)
  • Default permission is User; Editor is for collaborative curation

​
FAQ

No. Remove from collection only takes the app out of that Collection. The app stays in its original space, keeps its owner, and remains in any other Collections it belongs to.
Only if you give them Editor or Owner access. The default User access lets them use the apps but not change the Collection.
Yes. Every Collection role, including Editor and Owner, gives User access to each app inside, so recipients can use the apps but not edit them. Removing someone’s access to the Collection removes the app access they had through it.
Open the Collection, click Share, find the recipient, and choose Remove access from their role dropdown. They lose the Collection and any apps they could reach only through it. Their past sessions aren’t deleted.
The app stays in the Collection, but its card has no Launch button, so recipients can’t use it until it’s published again.
No. Collections have no public setting. You share a Collection with specific people, groups, or organizations from the Share dialog.
No. A Collection holds apps only. For nested groupings, use multiple Collections.
No technical limit. Aim for 5 to 20 to keep the Collection readable for recipients.
Last updated: 09-30-2026 Contact us at [email protected]